home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Internet Info 1993
/
Internet Info CD-ROM (Walnut Creek) (1993).iso
/
inet
/
internet-drafts
/
draft-ietf-x25mib-ipox25mib-05.txt
< prev
next >
Wrap
Text File
|
1993-06-07
|
2KB
|
61 lines
A new Request for Comments is now available in online RFC libraries.
RFC 1461:
Title: SNMP MIB extension for Multiprotocol Interconnect
over X.25
Author: D. Throop
Mailbox: throop@dg-rtp.dg.com
Pages: 21
Characters: 47,945
Updates/Obsoletes: none
This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in TCP/IP-based internets.
In particular, it defines objects for managing Multiprotocol
Interconnect (including IP) traffic carried over X.25. The objects
defined here, along with the objects in the "SNMP MIB extension for
the Packet Layer of X.25", "SNMP MIB extension for LAPB", and the
"Definitions of Managed Objects for RS-232-like Hardware Devices",
combine to allow management of the traffic over an X.25 protocol
stack. The RFC is a product of the X.25 Management Information Base
Working Group of the IETF.
This is now a Proposed Standard Protocol.
This RFC specifies an IAB standards track protocol for the Internet
community, and requests discussion and suggestions for improvements.
Please refer to the current edition of the "IAB Official Protocol
Standards" for the standardization state and status of this protocol.
Distribution of this memo is unlimited.
This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@CNRI.RESTON.VA.US. Requests to be added
to or deleted from the RFC-DIST distribution list should be sent to
RFC-REQUEST@NIC.DDN.MIL.
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to "rfc-info@ISI.EDU" with the message body
"help: ways_to_get_rfcs". For example:
To: rfc-info@ISI.EDU
Subject: getting rfcs
help: ways_to_get_rfcs
Requests for special distribution should be addressed to either the
author of the RFC in question, or to NIC@NIC.DDN.MIL. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
Submissions for Requests for Comments should be sent to
RFC-EDITOR@ISI.EDU. Please consult RFC 1111, "Instructions to RFC
Authors", for further information.
Joyce K. Reynolds
USC/Information Sciences Institute